Actually: could defer the semver-major designation in the short term by making the default do no extension validation (i.e. no default) and set the default to ['js'] in v2.0.

@sindresorhus can you set settings in XO? would that resolve your issue?

How does the settings thing work? Is it something ESLint provides or is it custom to this plugin?

It'd just be a normal shared ESLint setting spec'd in an .eslintrc, i.e.

---
# shown for context. I assume you configure this somewhere
plugins:
  - xo
  - import
  # etc.

# so it would need this too, until the default is set in v2 of import plugin:
settings:
  import/extensions: [ .js ]

I'm not sure exactly how XO wraps ESLint, so it's not obvious to me where you're setting up plugins.

@benmosher Ok, I didn't know about that ability. Should work for us as we just supply ESLint with a config file: https://github.com/sindresorhus/xo/blob/cc49ed4ec069bcd0885ac54513bc76b964bcdcd3/config/plugins.js

Actually, this might be a better place for it: https://github.com/sindresorhus/eslint-config-xo/blob/master/index.js

Looks like you're leveraging this for the XO executable, right? or is this just a mirror? Either way, probably ought to be there for consistency (and optimally only there for DRYness).

Either way, I'll make the change to have no default for now and open a new issue to default to ['.js'] in v2, so this can go out with 1.7.

@benmosher That's just an XO implementation detail. I don't put plugin stuff in the pure ESLint config, since you're then forcing the user to manually install each plugin. That's why it's in the XO binary instead, as it can just be dependencies there.

But yeah. Sounds good to me.

Ah, sure, that makes sense.

FWIW, the settings don't require the plugin to be installed, it's just a map that is shared by all rules (including the baked-in ESLint ones).

I just prefix mine with import/ to avoid conflicts. So you could put it wherever, though it probably does make sense to colocate it with the plugin reference.

I hope someone can help with this, it is driving me crazy. Atom / Eslint will not recognize my ./src/components/header.js import coding.. Attached is a photo of the sim error and such.

I am very new to this and I have tried to fix it by making a new "rule" but I am not sure if I am doing it right. Could someone please help me with this walk through?

What rule do I have to add?

@LycanHalcyon that should be

import Header from './src/components/header.js'

the syntax error is because you're missing the quotes around the file path.